|
|
The Websydian 4.01 release is a service release for Websydian 4.0 and includes the changes described below.
The Websydian DOM implementation in TransacXML has been changed on the Windows platform. Previous versions of the DOM implementation used VBScript to interface with the MSXML parser, whereas for this release the native C++ interface is used.
This has advantages like improved performance, but most important the functions using TransacXML no longer needs to scope a panel object as required by the VBScript engine. This panel turned out to cause memory leaks when the function exited without opening the panel.
TransacXML now supports automatic generation of DTD’s (Document Type Definition). DTD generation can be used to create a DTD representing an implemented XML data model. This can be used to verify the implemented model against a given DTD or to provide the DTD for construction of compatible web services. The created DTD can be transformed into other formats such as XML Schema or WSDL (Web Services Description Language) using 3rd party tools such as XML Spy.
Based on feedback from users of TransacXML two productivity-enhancing features have been added to TransacXML.
First, GetFirstOccurence is introduced as a fast way to retrieve the first element of a given type in a document. This function eliminates traversing complex XML structures and increases development productivity significantly.
Second, direct references to the previous and next elements of the same type are now returned from the data access functions (SingleFetch, UpdateRow, DeleteRow and InsertRow) eliminating additional navigation for trivial tasks such as fetching a list of records.
This release contains a number of fixes for the currently supported Websydian versions 3.0, 3.1, and 4.0. In the latest fix package we have addressed bugs in the Java and iSeries runtime environment.
| Architecture | Platform | Description |
|---|---|---|
| All | iSeries | Potential memory leak in iSeries runtime objects |
| DWA | All | Websydian Server fails when receiving information about unknown tokens |
| Websydian Server wrongfully reported other instances of the Websydian Server started | ||
| Websydian Web Server Component only adds session for request type application/x-www-form-url-encoded | ||
| Websydian Web Server Component fails if user presses cancel button during download of binary data | ||
| Java | Error in Application Service handling of binary data buffering | |
| iSeries | Starting Application Services using the command STRAS now takes routing data from job description | |
| Potential deadlock between Websydian Server and Application Service Controller |
Websydian 4.0 and CA Plex 5.1 includes full support for J2EE. The Websydian J2EE architecture is a J2EE enabled extension of the DWA architecture.
Please refer to the J2EE section for more information.
Websydian 4.0 now also includes full support for XML on the Java platform. This can be used to implement XML based solutions on any platform, including the iSeries. For more information refer to the TransacXML section.
DWA, the Websydian architecture for high performance, scalability, and platform flexibility, is now the primary architecture of Websydian.
The CGI-based alternative, Classic Websydian Architecture (CWA), will still be developed and supported, but not all new features will be available in CWA.
Please refer to the DWA section for more information.
The licensing model of DWA has been changed to include three levels of licenses: Websydian Server Basic, Websydian Server Pro, and Websydian Server Enterprise. Please refer to the DWA licensing section for further information on the licensing model.
Customers with a valid PKA license can upgrade to the Websydian Server Enterprise license free of charge.
Further inheritance must be specified for the Application Service Listener function when upgrading existing DWA/PKA applications. Please refer to the Application Service Listener implementing section for further information.
The Token Server has been replaced by the Websydian Server. The Websydian Server is the central repository for application information, and possesses the ability to control the different parts of the application as well as the overall application state.
Please refer to the Websydian Server section for more information.
For most Websydian patterns a number of library objects must be generated and built. Historically, these have been placed in an appropriately named package (xxxObjectsToGenerateAndBuild).
These objects are now moved to similarly named Subject Areas. This solves a number of problems arising under Java, where packages have a different meaning than under Windows and RPG.
The existing packages are empty and renamed to useAppropriateSubjectArea. Please refer to the Generate and Build section for more details.
The documentation distributed with Websydian has been changed to allow for global searches in the documentation. This implies that it is no longer possible to use the context-sensitive help in CA Plex for Websydian functions.
The dispatcher now allows parameters in the first request. This can be used to send initial parameters when launching a Websydian application.
The Windows CGI Websydian Web Server Component executable (CgiRelayS.exe) now uses its own name to construct the filename of the ini file. This means that it is now possible to create a copy of the Windows CGI Websydian Web Server Component executable and specify an ini file specific to the copy (e.g. MyRelayService.exe - MyRelayService.ini).
The Frameset page generator now URL encodes the links to the included frame pages. This is required if some of the specified parameters in the links contain unsafe characters.
An error in the C-Wrappers calling the ANSI C DWA layer causing memory overrun on returned char pointers has been fixed.
The Upgrade Guide to Version 4.0 technical paper contains detailed instructions on what needs to be done when migrating a Websydian model from version 3.1 to 4.0.
Online documentation - Websydian v6.5